fix: use npx for portable completion scripts#76
Merged
Aslemammad merged 2 commits intomainfrom Oct 18, 2025
Merged
Conversation
🦋 Changeset detectedLatest commit: 98d8dbb The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Aslemammad
approved these changes
Oct 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When users generate completion scripts via
npx @bomb.sh/tab, the generated scripts contained absolute file paths pointing to temporary npx cache directories. this will cause the completions to break when users re-install or update the package ( the hash cahnges ) or when scripts are shared between users, or when users runnpm cache cleanas for a fix, I used
npxsince its installed wherever node is installed, and also kept using absolute path for testing local changes and maintanance.so
node dist/bin/cli.jsuses absolute path andnpx @bomb.sh/tabusesnpxcommand